Methods, devices and systems for medical code event information tracking

ABSTRACT

A device is configured to process medical-event related information, such as associated with a medical code event, such as by receiving medical-event related information, recording medical event information with timestamps, generating additional medical information, displaying medical events and additional medical information on media display, visual indicators, and user devices to provide real-time notifications of recorded and reminders for upcoming medical events, and sending medical events with timestamps and additional medical information to other devices for further processing. The device may be configured as a code clock which includes an analog clock.

RELATED APPLICATION DATA

The present application claims priority to U.S. Provisional ApplicationSer. No. 63/111,684, filed Nov. 10, 2020, and U.S. ProvisionalApplication Ser. No. 62/967,138, filed Jan. 29, 2020.

FIELD OF THE INVENTION

The present invention relates to medical devices.

BACKGROUND OF THE INVENTION

Hospitals frequently use code names to alert staff to various events,and particularly emergency events. The hospital may communicate aparticular code, such as through an intercom system, in order to directappropriate staff to respond to the event (“code event”). For example, a“Code Blue” event typically designates a medical emergency, such ascardiac or respiratory arrest.

In such an emergency event, a medical team may respond to a patient,such as in their hospital room, an ER or the like. The team might becomprised of one or more doctors, one or more nurses, a pharmacist, etc.

As with any medical procedure, it is desirable to record informationabout the patient and the actions taken by the medical personnel.Generally, such information is logged manually, such as by writingactions or information on a paper ledger. However, an emergency event isgenerally very time-sensitive, wherein the medical team is attempting toperform a variety of life-saving actions in a very short period of time.Further, a variety of members of the team may be performing differentactions at different times. As a result, in these and other situations,various information may not be accurately captured, including by failingto log certain actions entirely, by logging incorrect information aboutthe time an event occurred or action was taken, personnel involved, etc.

A solution to these and other problems is desired.

SUMMARY OF THE INVENTION

The described invention is an innovative solution to the problem oferrors and omissions resulting logging medical events manually duringcode events.

Embodiments of the invention comprise methods, systems, and devices ofprocessing medical-event related information, such as receivingmedical-event related information, recording medical event informationwith timestamps, generating additional medical information, displayingmedical events and additional medical information on media display,visual indicators, and user devices to provide real-time notificationsof recorded and reminders for upcoming medical events, and sendingmedical events with timestamps and additional medical information toother devices for further processing. One embodiment of the invention isa device in the form of an analog clock.

As an aspect of the invention, a plurality of systems and devices may bein direct or indirect communication with each other to send and receivemedical-event related information, timestamps, and additional medicalinformation generated by any one of such systems or devices, such thatthe media displays and visual indicators on each of the plurality ofdevices may display information sent by any one of the plurality ofsystems or devices.

As another aspect of the invention, medical-event related informationmay be sorted into confidential medical information and non-confidentialmedical information, and confidential medical information is recordedand sent with additional security protocols and features to protectpatient confidentiality.

Likewise, in accordance with such a system, the plurality of devices incommunication with each other to send and receive medical-event relatedinformation may be sorted into devices of various clearance levels, suchthat devices of certain clearance levels may send, receive, and displayall confidential medical information, while devices of differentclearance levels may send, receive, and display some or no confidentialmedical information.

Further objects, features, and advantages of the present invention overthe prior art will become apparent from the detailed description of thedrawings which follow, when considered with the attached figures andtables in the Appendix.

DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically illustrates internal components of an event device;

FIG. 2 illustrates the external components of one embodiment of theevent device;

FIG. 3 illustrates the flow diagram of the software applicationassociated with the event device;

FIGS. 4A-E illustrate embodiments of graphical user interfaces ordisplays of the software application associated with the event device;

FIGS. 5A-C illustrate the event device in direct and indirectcommunication with the software application associated with the eventdevice;

FIG. 6 illustrates the event device in direct and indirect communicationwith a plurality of software applications;

FIG. 7 illustrates the event device in direct and indirect communicationwith a plurality of software applications, where software applicationsare set to either administrator mode or read-only mode.

DETAILED DESCRIPTION OF THE INVENTION

The following description sets forth numerous specific details toprovide a more thorough description of the present invention. It will beapparent, however, to one skilled in the art, that the present inventionmay be practiced without these specific details. In other instances,well-known features have not been described in detail so as not toobscure the invention.

Aspects of the invention comprise methods, devices and systems fortracking or recording information associated with medical events, suchas information associated with a patient medical event, and preferably amedical code event, relative to one or more associated personnel such asmedical personnel (doctors, nurses, surgeons, etc.).

FIG. 1 illustrates one embodiment of an event device 1 in accordancewith an embodiment of the invention. In one embodiment, the event device1 comprises various electronic components in communication with oneanother through a device bus 20. The electronical components maycomprise a processor 30, a non-secure memory 40, a secure memory 50, oneor more communication interfaces 60 used to communicate with one or moreinput devices 70 and one or more output devices 80. One or more of thecomponents of the event device 1 may be associated with a housing 10,such as by being contained within or mounted to the housing 10.

The non-secure memory 40 stores machine-readable code 41. The securememory 50 stores medical event information. In one embodiment, thesecure memory 50 may include read and/or write protect features tocontrol access to the stored information. One embodiment of such readand/or write protect feature is requiring a user to enter a password orother authorization to access, modify or delete information associatedwith the secure memory 50.

The CPU or processor 30 executes the machine-readable code 41. In oneembodiment, the CPU or processor may be configured to encryptinformation routed to the secure memory 50.

Input devices 70 may comprise recording devices 71 (such as microphone,cameras, sensors, etc.), reading devices 72 (such as magnetic stripereader, chip reader, RFID tag reader, or optical scanner, etc.), and oneor more data input devices 73. Data input devices 73 may comprise one ormore input/output (I/O) devices 91, one or more user devices 92, one ormore medical devices 93, and/or one or more external servers 94.

I/O devices may comprise keyboard, mouse, button pad, touch screen, I/Oports, etc. Such I/O interfaces may be of various types, such as wired(USB, DVI, HDMI, multi-pin serial or parallel, etc.) and/or wireless(Bluetooth, Wi-Fi, etc.).

User devices 92 may comprise smartphones, tablets, computers, etc., orinterface for interfacing to such user devices 92.

Medical devices 93 may comprise devices used to measure patient data orvalues (such as heart monitor, blood pressure monitor,electrocardiogram, etc.) and/or devices used to apply medication ortreatment.

External servers 94 may implement databases to process and/or storeinformation and provide interface to communicate with such databases,such as websites. For example, the record of information associated witha code event of a patient might be transmitted from the event device 1to a patient's electronic hospital record for association therewith.

Output devices 80 might comprise media output devices 81 such as one ormore visual or video displays (such as CRT, plasma, LCD, LED, OLED,etc.) and/or one or more audio output devices (such as one or morespeakers), one or more visual indicators 82 (such as one or moreindicator lights, which lights might be of one or more colors, includingdifferent colors, and/or capable of being illuminated at differingbrightness), one or more document output devices (such as printers, faxmachines, etc.), and/or one or more data output devices 84 (such as oneor more user devices 92, one or more medical devices 93, and/or one ormore external servers 94).

Communication between one or more communication interfaces 60 with oneor more input devices 70 and/or one or more output devices 80 may bewired (via a cable or ethernet) or wireless (via a network such as theInternet, a hospital LAN or WAN, etc.), and uses various communicationprotocols, including TCP/IP or others.

In some embodiments, components of the event device 1 might not beassociated with the housing 10. For example, if the event device 1includes an I/O device 91 such as keyboard and mouse, such devices mightbe located on a work surface near the event device 1, such that themouse and keyboard communicate with the event device 1 via thecommunication interfaces 60.

Although not illustrated, the event device 1 may be powered by a primarypower supply, such via an electrical outlet, and include a secondary orback-up power supply, such as one or more batteries.

In one embodiment, the operation of the event device 1 can be initiatedthrough information via input devices 70, such as information associatedor related to a code event. In one embodiment, code events communicatedto input devices 70, such as by voice command through a recording device71 or touch command through an i/o device 91 or user device 92, mightautomatically trigger the event device 1 to start recording information.

Upon proper initiation, the event device 1 is preferably configured toreceive information regarding persons (including the patient and/orassociated medical personnel) associated with a medical event, such as amedical code event, via input devices 70.

In one embodiment, the event device 1 is configured to receiveinformation regarding staff personnel present at the code event. Suchinformation might include RFID tags of medical personnel who are in thevicinity of the event device 1, magnetic stripes on personnel badges,etc.

In one embodiment, the event device 1 is configured to receive patientinformation. Such information might include patient IDs (such as abarcode or label) of patients in the vicinity of the event device 1. Inone embodiment, patient information received by the event device 1 mayprompt the event device 1 to communicate with external servers 94 toretrieve additional information regarding patient data or values (suchas patient height, weight, medical history, etc.).

In one embodiment, the event device 1 is configured to receiveinformation via input devices 70 regarding activities occurring during acode event. The form of such information might include voice input (suchas voice commands), audio input (such as recorded audio), visual input(such as recorded pictures and/or videos), touch input, or input fromexternal medical devices (such as heart monitor, blood pressure monitor,electrocardiogram, etc.). The content of such information might includeoccurrence of medical events (such as application of treatment andmedication), media recordings of medical events (such as audio, image,or video recordings), patient data or values (such as heart rate, bloodpressure, etc.), and or media recordings of patient data or values (suchas audio, image, or video recordings of patient appearance or behavior).

The event device 1 preferably stores the information received in thesecure memory 50. Where applicable, the event device 1 preferablyapplies timestamps to the stored information, such as to document theoccurrence of certain events or activities and their respective time ofoccurrence.

In one embodiment, the event device 1 may use patient data or values tocustomize the desired medication or treatment or otherwise generate andoutput additional medical information based upon the received medicalevent information. For example, during a code event comprising pediatricarrest, the event device 1 may retrieve the patient data or values fromexternal servers 94, as discussed above, then use some of the retrievedinformation, such as the patient's weight in Kg, to calculate thecorrect dosage of a desired medication based upon the patient's weight.As discussed above, the event device 1 may also receive such patientdata or values through other input devices 70.

In one embodiment, the event device 1 communicates with data outputdevices 85 to report recorded information and/or to request additionalinformation.

In an embodiment, the event device 1 may cause document output devicesto print information event strips after recording of a code event hasterminated.

In one embodiment, the event device 1 may be configured to displayinformation through output devices 70. Displayed information includepatient data or values (such as heart rate, heart rhythm), a list ofmedication administered and their respective time of administration,calculated timing of upcoming medications to be administered and/orrecommended medications from external devices.

As one example, during a particular code event, the event device 1 mightreceive a list of administered medication through its input devices 70,record the list of medication with timestamps, and display said list ofadministered medication through its output devices 80. Simultaneously,the event device 1 might automatically calculate the timing for the nextapplication of some or all the medications on the list of medicationsthe event device 1 recorded. Upon calculating the timing, the eventdevice 1 might then display alerts when the medication is to beadministered via the output devices 80 (such as display of visual oraudio notification 81, visual indicators 82, alerts to user devices 92,or notifications to medical devices 93, etc.).

As another example, during a particular code event, the event device 1might communicate with a first external server 94 to deliver informationregarding patient data or values indicating the necessity for immediatetreatment. The event device 1 might then receive information from saidfirst external server 94 identifying the best medications or othertreatments and associated dosing and the scheduling of such medicationsor treatment. The event device 1 might, upon receiving suchidentification, communicate with a second external server 94 to provideinstruction for such medication or treatment, and simultaneously displayalerts when recommended medication is to be administered via otheroutput devices 80.

As another example, during a particular code event, the event device 1might receive information from an external server 94 which identifiesmedications or other treatments to be administered. The event device 1might identify an interaction problem such as overlapping or conflictingmedications or treatments. The event device 1 might then communicatesuch problem to the external server 94. In this manner, the event device1 may serve as a “smart” device relative to the activities which areoccurring during the particular code event.

In one embodiment, the event device allows the user to recall recordedinformation. For example, if the user wishes to determine whether themedication epinephrine was given, and if so, when, or how many times,the user may activate the recall feature through the one or more inputdevices 70. Upon proper input to select the information the user wishesto recall (in this case, the application of epinephrine to the patient),the event device 1 may cause the output devices 80 to provide audiofeedback and/or visual display of the information (for example, an audioread-out and/or a video or image display of whether epinephrine wasgiven, and if so, when and how many times).

In another embodiment, the machine-readable code/software 41 in theevent device 1 (alone or as coupled to external systems or servers) maybe updated with new algorithm and/or information regarding current bestpractice in treatments and medication.

FIG. 2 illustrates one embodiment of the event device 1. In thisembodiment, the event device 1 is configured as an event clock 100,which has a form similar to a clock. In the preferred configuration, theevent clock 100 is an analog clock with moving physical hands 110 andtraditional indicators and numbering to display time 111. In otherembodiments, the event clock 100 might be displayed as a graphicalrepresentation on a display or a portion of a display.

The event clock 100 might thus be mounted on a wall, such as within ahospital patient room, hospital emergency room, etc. The output devices80 may be located at the front of the event clock 100, while theremaining components in housing 10 may be located at the back of theevent clock 100.

In one embodiment, the event clock 100 is configured to display one ormore icons regarding particular events or event-related information,such as an icon that indicate compressions 120 (such as via a “CPR” iconor symbol), shocks 130 (such as via a “lightning bolt” icon or symbol),pulse checks 140 (such as via a “heart” icon or symbol), and heartrhythms observed 150 (such as via a EKG icon or symbol).

In one embodiment, icons such as CPR 120, shocks 130, and pulse checks140 will glow while the specific treatment or measurement is beingperformed. In another embodiment, icons such as CPR 120, shocks 130, andpulse checks 140 will change color, along with audio prompts via outputdevices 80, to provide secondary information. For example, afterreceiving information from input devices 70 indicating a compressionshould be performed, the CPR icon 120 might blink for 2 minutes toindicate the appropriate duration of compression. As another example, 2minutes after the application of compression, the pulse check icon 140might blink to notify a pulse check following compression is due.

In one embodiment, a number indicator 131 below the shocks icon 130indicates the number shocks applied to the patient.

In one embodiment, intervening events and inputs may cause a baseconfiguration of the event clock 1 (or its output) to be modified. Forexample, relative to the above example, the base configuration might befor the CPR icon 120 to blink for 2 minutes upon receiving informationfrom input devices 70 indicating a compression should be performed for 2minutes. On the other hand, if the event device 1 receives informationfrom input devices 70 that compression was performed for 3 minutes andthen a STAT echo was performed to check heart activity, the event device1 might cause the blinking light in the CPR icon 120 to turn off and notturn on again without further prompts.

In one embodiment, the media output devices 81 include a speaker on thefront of the event clock 132 to allow better audio output, particularlyfor the recall feature discussed above.

In one embodiment, various output devices 70 on the event clock 100provide visual and audio feedback for medications. One preferredembodiment is a set of visual indicators 82 comprising of lightindicators 160. In one embodiment, the light indicators 160 comprise oneor more lights positioned relative to the time indicators 111, such asat each 1-minute interval of the clock. In one embodiment, each light onthe light indicators 160 is capable of displaying different colors toindicate different color-coded medications. In another embodiment,instead of circular dots, the light indicators may comprise letters todisplay the first letter of a particular medication.

The light indicators 160 may be activated in various manners to providemedication-related information. For example, a solid light may indicatethat a particular medication is available to be given at the designatedtime. A blinking light may indicate that a particular medication is dueat a particular time. Such blinking light may continue to blink,following the minute hand 110 as it sweeps, until the event device 1receives information from its input devices 70 that medication is givenor cancelled, or the event code is terminated.

In one embodiment, the event clock 100 may comprise audio output devices81. In one preferred embodiment, the event clock 100 comprises an audiodevice 81 configured to emit at least two alert sounds. One alert soundmay comprise a “due soon” alert to indicate that a medication is duewithin a designated amount of time (such as 30 seconds). The other alertsound may comprise a “due now” alert, indicating that a medication isdue. Such alert sounds are preferably short chirps, lasting about threeto five seconds.

In one embodiment, if the event device 1 does not receive informationthat medication is given when due, after the alert sound expires, theevent clock 100 may continue to display a visual indicator 82 such as alight indicator 160.

In one embodiment, termination of operation of the event clock 1 may beinitiated by input received from input devices 70.

In one embodiment, the event device 1 may communicate with one or moreuser devices 92. In the case where the user device 92 is one or moremobile communication device (such as a smartphone, a tablet, asmartwatch, etc.), the invention provides a uniquely configured ACT Nowsoftware application (“ACT Now App”) 500 which the user can download andinstall on such mobile communication device.

FIG. 3 illustrates a flowchart of one embodiment of the ACT Now App 500comprising of an ACT Now icon 510, a user login page 520, a patientcategory selection 530, and time sync feature 540, a main page 550, andan exit page 614.

In a preferred embodiment, each user input, selection, or command in theACT Now App 500 can performed with voice commands.

The user login page 520 allows user to provide user credentials 521 viamanual input 823 (such as username and password, identification code,etc.) or via readable information 524 (such as a badge, barcode, or QRcode 524, which the ACT Now App 500 may scan or read).

The user login page also allows user to initiate communication 522between the ACT Now App 500 and the communication interfaces 60 of anyevent devices 1 in proximity.

The patient category selection 530 allows users to select “ADULT” 531for adult patients, “PEDS” 532 for underaged patients, and “DEMO” 533for a teaching mode where various code events may be rehearsed forlearning purposes and no critical information will be stored. Propersection of patient category 530 will prompt the ACT Now App 500 to loadfeatures corresponding to each selection.

The time sync 540 feature allows users to sync the ACT Now App 500timer, which the ACT Now App 500 uses to apply timestamps to recordedevents, where applicable. The user can sync the ACT Now App 500 timereither via manual entry 541 (where the user can manually enter thecurrent time 543) or automatic entry 542 (where the ACT Now App 500 willdisplay devices in its proximity 544, and upon proper selection ofproximity devices, the ACT Now App 500 will automatically sync its timerwith the time used by the selected proximity device). Upon proper syncof the ACT Now App 500 timer, the ACT Now App 500 will begin its timer546.

In one embodiment, the main page 550 might be configured to display awide variety of other information and/or implement other functionality.For example, the ACT Now App 500 might be configured to replicate theinformation the event device 1 receives via its input devices 70, and/orto display information the event device 1 displays via the outputdevices 80.

In one preferred embodiment, it may be desirable that the event device 1not display detailed patient data or values to protect a patient'sprivate information. Thus, in one embodiment when one or more ACT NowApps 500 are included, the event device 1 might only display generalinformation, such as time, etc., and the event device 1 or theassociated system may be configured to cause each ACT Now App 500 todisplay any detailed patient data or values (including information aboutthe patient or associated events, drugs, or procedures, etc.). Forexample, a nurse might administer a drug to a patient. The nurse mightprovide a voice input to the event device 1 regarding the administereddrug. The event device 1 may process that information, including timestamping and storing the event information. However, the event device 1might not display information regarding the event. Instead, informationregarding the administered drug might only be displayed on ACT Now App500.

In one embodiment, the ACT Now App 500 may provide functional back-up tothe event device 1. For example, if the event device 1 malfunctions andfails to receive information via its input devices 70, the user maymanually enter that information to the ACT Now App 500. Similarly, ifthe event device 1 malfunctions and fails to display information via itsoutput devices 80, the ACT Now App 500 may continue to displayinformation to the user.

As one example, upon applying compression to a patient, the user cantouch the CPR icon 560, prompting the ACT Now App 500 to record theevent with timestamp 561. In one embodiment, the ACT Now App 500 maydeliver the recorded information to an event device 1 and other outputdevices 80.

As another example, upon applying treatment to patient airway (such asbag valve masks or ventilator), the user can touch the AIRWAY icon 570,prompting the ACT Now App 500 to display a list of airway options 571,allowing the user to select common airway treatment. Where applicable,the selection of an airway option might prompt the ACT Now App 500 todisplay a list of values related to the selected airway option 572,allowing the user to record the airway option values (for example, thelength of endotracheal tube used for intubation). Upon proper input ofairway option and airway option values, the ACT Now App 500 may recordthe input with timestamp 573. In one embodiment, the ACT Now App 500 maydeliver the recorded information to an event device 1 and other outputdevices 80.

As another example, the user might want to periodically record patientdata or values related to rhythm (such as pulse or electrocardiogramdisplays). The user can touch the RHYTHM icon 580, prompting the ACT NowApp 500 to display a list of rhythm options 581, allowing the user toselect common patient data or values related to rhythm. Upon properinput of rhythm values, the ACT Now App 500 records the input withtimestamp 582. In one embodiment, the ACT Now App 500 may deliver therecorded information to an event device 1 and other output devices 80.

As another example, the user might want to periodically record otherpatient data or values (such as blood pressure or blood sugar). The usercan touch the PATIENT icon 590, prompting the ACT Now App 500 to displaya list of patient data or values 591, allowing the user to input commonpatient data or values not related to rhythm. Upon proper input ofpatient data or values not related to rhythm, the ACT Now App 500records the input with timestamp 592. In one embodiment, the ACT Now App500 may deliver the recorded information to an event device 1 and otheroutput devices 80.

As another example, the user might want to record medications ortreatment given to the patient. Upon touching the MED icon 600, the ACTNow App 500 might display a list medication options 601, allowing theuser to select common medications or procedures. Where applicable, theselection of a medication option might prompt the ACT Now App 500 todisplay a list of values related to the selected medication 602,allowing the user to record the amount of medication applied. Uponproper input of medication option and medication value, the ACT Now App500 records the input with timestamp 603. In one embodiment, the ACT NowApp 500 may deliver the recorded information to an event device 1 andother output devices 80.

Where applicable, the ACT Now App 500 might also initiate a stopwatchand display the stopwatch, name of medication, and number of medicationon its main page 550, and notify user of the next application ofmedication or treatment. For example, when the user properly inputs afirst injection of epinephrine, the ACT Now App 500 might initiate astopwatch, display “EPIx1” and the stopwatch on its main page 550. In anembodiment, the ACT Now App 500 might also display visual (such asblinking stopwatch timer and blinking “EPIx1” display) and/or audio(such as the “due soon” or “due now” alert sounds) prompts to notify theuser of next injection of epinephrine at the appropriate time interval.Upon the second injection of epinephrine, the ACT Now App 500 mightrestart the stopwatch and display “EPIx2” and the stopwatch on its mainpage 550.

In one embodiment, the ACT Now App 500 allows a user to initiatetermination of a code event using the STOP icon 610. In one embodiment,the user must hold the STOP icon for 3 seconds or longer (to, forexample, prevent inadvertent activation of the “STOP” button). In anembodiment, when the user properly initiates termination, the ACT NowApp 500 may display additional end options 611 (such as patient death orpatient return to normal state). Upon proper input of end options, theACT Now App 500 records the input with timestamp 612, stops the ACT NowApp 500 timer and all active stopwatches, and displays the exit page614.

In an embodiment, the exit page 614 may allow users to enter additionalinformation. For example, user may provide additional informationregarding tubes and IV access points. Such information may be timestamped and delivered to external servers 94. Additional information mayalso include identification of one or more medical staff. In anembodiment, a physician-specific five letter acronym may be entered toretrieve the user's electronic signature. One or more physician acronymsmight be entered. This allows for ICU physicians, residents, or internsto be recorded.

In one embodiment, the ACT Now App 500 may be configured to providemedication suggestions based on user input of patient data or values592. In one embodiment, the medication suggestions are displayed on theACT Now App 500 but not displayed on the event device 1.

In one embodiment, the ACT Now App 500 may allow users to requestrecorded information. For example, the user may have forgotten whether aspecific medication or treatment was given (for example, epinephrine),or when or how many times said medication or treatment was given. Uponselecting the RECALL icon 620, the user may be able to select categoriesof medical events on a display recall options page 621 (for example,selecting “medication” under listed medication and treatment category),and further select specific medical events on a display recall optionvalues page 622 (for example, selecting “epinephrine” under listedmedications). Upon proper selection of the information the user wishesto recall, the ACT Now App 500 may provide audio feedback and/or visualdisplay of the information (for example, an audio read-out and/or avideo or image display of whether epinephrine was given, and if so, whenand how many times).

In one embodiment, the ACT Now App 500 may be updated throughdownloading new or updated information.

FIG. 4A illustrates the design of an embodiment of the ACT Now icon 510.

FIG. 4B illustrates the design of an embodiment of the user info page521 where the user can manually enter user credentials 523, and/or theexit page 614 where the user can enter further information and identifyadditional medical staff present.

FIG. 4C illustrates the design of an embodiment of the patient categoryselection page 530.

FIG. 4D illustrates the design of an embodiment of the main page 550,which displays analog clock synched up with an event device 1 or eventclock 100, any stopwatch and medication information 604, and the MED600, RHYTHM 580, AIRWAY 570, and STOP 610 icons.

FIG. 4E illustrates the design of an embodiment of the rhythm optionsdisplay page 581.

FIG. 5 illustrates an embodiment of a system where an ACT Now App 500might communicate directly with an associated event device 1. On otherembodiments, the communication may be indirect, such as via other userdevices 92 or external servers 94. As one example, the event device 1may provide information to an external server 94 which implements awebsite. The website may, in turn, cause the ACT Now App 500 to receiveand display said information. Similarly, the ACT Now App 500 may provideinformation to an external server 94 which implements a website, whichin turn may cause the event device 1 to receive and display saidinformation. An advantage to this system is if the event device 1malfunctions, each ACT Now App 500 can still communicate with other userdevices 81 or external servers 94 to provide information.

FIG. 6 illustrates an embodiment of a system where multiple ACT Now Apps500 are used, each ACT Now App 500 and the event device 1 may be syncedsuch that the event device 1 and all synced ACT Now Apps 500 may becontinually updated based upon information received by any input devices70. For example, an input to the event device 1 may be transmitted toeach synced ACT Now App 500. Similarly, an input to an ACT Now App 500may be transmitted to the event device 1 and each other synced ACT NowApps 500.

FIG. 7 illustrates an embodiment of a system where one ACT Now App 500may be designated as the system administrator. In this configuration,only the event device 1 or the administrator ACT Now App 500 may acceptuser input, while all other ACT Now Apps 500 are set to “view only” modeor status such that the other ACT Now Apps 500 may function as outputdevices 80 to display recorded information and notifications on theirmain pages 550, but may not function as input devices 70. This preferredembodiment of the system prevents multiple users from enteringduplicative or contradictory input of information.

In a preferred embodiment, users of the ACT Now Apps 500 may be assigneddifferent clearance levels. Depending on the user credential entered523, 524, the ACT Now Apps 500 may assign a clearance level to the userautomatically or by communicate with an external server 84 to retrievesuch assignment. Different clearance levels provide or limit the user'saccess to the type, nature, and/or format of information the user mayinput, or the ACT Now Apps 500 may display. For example, one clearancelevel may automatically assign the user of the ACT Now Apps 500 theadministrator role mentioned above.

Table 1 in Appendix A illustrates an example of specific use of theevent device 1 and ACT Now App 500 during the event code cardiac arrest,including possible time 1000 and corresponding events 1500, possiblevoice commands 2000 provided to input devices 70 of an event device 1such as an event clock 100, and corresponding responses, displays, andnotifications of medications and treatments due 2500 on the event clock100. Table 1 also illustrates corresponding user input 3000 to the ACTNow App 500 (due to either user preference or the event device 1malfunction), and possible responses, displays, and notifications ofmedications and treatments due 3500 on the ACT Now App 500.

Table 2 in Appendix A illustrates an example of specific use of theevent device 1 and ACT Now App 500 during the event code respiratoryarrest, including possible events 5000, possible voice commands 5500provided to input devices 70 of an event device 1 such as an event clock100, and corresponding responses, displays, and notifications ofmedications and treatments due 6000 on the event clock 100. Table 2 alsoillustrates corresponding user input 6500 to the ACT

Now App 500 (due to either user preference or the event device 1malfunction), and possible responses, displays, and notifications ofmedications and treatments due 7000 on the ACT Now App 500.

As illustrated in the figures and tables referenced above, the devicesand system of the invention replace hand-written code sheets and providea real time, accurate description of resources utilized, medicationsgiven, and interventions performed. This information may establish, forexample, that every option was exhausted in the event of a death eventfor legal or malpractice inquiries, or a timestamp of when ROSC wasachieved for patient documentation, research, or education. Theinvention will greatly reduce human error and omissions fromhand-written code forms, particularly in hectic and fast-paced codeevents.

It will be understood that the above-described arrangements of apparatusand the method there from are merely illustrative of applications of theprinciples of this invention and many other embodiments andmodifications may be made without departing from the spirit and scope ofthe invention as defined in the claims.

What is claimed is:
 1. A method of processing medical-event relatedinformation comprising: receiving medical-event related information viaone or more communication links from one or more input devicescomprising one or more user devices and/or one or more external serversused to process medical information, such medical information comprisingnotification of a medical code event and information relating to themedical code event, said information comprising one or more of patientdata or values, medical personnel present, prescribed medications andtreatments, medical events relating to the measurement of patient dataor values, measurement of patient responses, and application of saidmedications and said treatments; applying timestamps to said informationregarding said medical code event; storing said information regardingsaid medical code event in one or more memory devices; generating, fromsaid information regarding said medical code event, additional medicalinformation comprising one or more of: recommended medication,recommended treatment, recommended values for said recommendedmedication and said recommended treatment, recommended timing forapplication of said recommended medication and said recommendedtreatment, and information identifying any error or conflict in receivedmedical information; and generating one or more outputs related to saidinformation regarding said medical code event and/or said generatedadditional information regarding said medical code event.
 2. The methodof recording medical-event related information of claim 1 furthercomprising sorting said received medical-event related information andadditional medical information into confidential medical information andnon-confidential medical information; storing said confidential medicalinformation in a secure memory device with one or more levels ofsecurity protocols and/or features to control the ability to read, add,modify, or delete said confidential information; sending saidconfidential medical information to said one or more output devices viaone or more secure communication links applying one or more levels ofsecurity protocols and/or features to control the ability to read, add,modify, or delete said confidential information; storing saidnon-confidential medical information in a non-secure memory device withone or more levels of security features to control the ability to read,add, modify, or delete said confidential information, wherein said oneor more levels of security protocols and/or features in said non-securememory device is lower than said one or more levels of security featuresin said secure memory device; and sending said non-confidential medicalinformation to output devices via one or more non-secure communicationlinks applying one or more levels of security protocols and/or featuresto control the ability to read, add, modify, or delete said confidentialinformation, wherein said one or more levels of security protocols orfeatures in said non-secure communications link is lower than said oneor more levels of security protocols or features in said securecommunications link.
 3. The method of processing medical-event relatedinformation of claim 1, wherein sending said received medical events andadditional medical information to said one or more media displaydevices, one or more visual indicators, and/or one or more user devicescausing display of some or all of said medical events and some or all ofsaid one or more said additional medical information on said one or moremedia display devices, one or more visual indicators, and/or one or moreuser devices.
 4. The method of processing medical-event relatedinformation of claim 1, wherein sending said additional medicalinformation to one or more medical devices causes said one or moremedical devices to apply said recommended medication and saidrecommended treatment at said recommended values and said recommendedtiming.
 5. The method of processing medical-event related information ofclaim 1, wherein delivery said medical events, said timestamps, and saidadditional medical information to said one or more user devices and/orone or more external servers causes the data stored in said one or moreuser devices and/or one or more external servers to be updated with saidmedical events, said timestamps, and said additional medicalinformation.
 6. A device for processing medical-event relatedinformation comprising a housing; a processor; a memory; a device busused for communication between said processor and said memory; one ormore input devices comprising at least one of: one or more recordingdevices, one or more reading devices, one or more input/output devices,one or more user devices, one or more medical devices, and/or one ormore external servers; one or more one output devices comprising atleast one of: one or more media output devices, one or more visualindicators, one or more document output devices, said one or more userdevices, said one or more medical devices, and/or said one or moreexternal devices; one or more communications interfaces used tocommunicate between said device bus, said one or more input devices, andsaid one or more output devices; one or more communication links usedfor communication between said device bus, said one or morecommunication interfaces, said one or more input devices, and said oneor more output devices; machine-readable code stored in said memory andexecuted by said processor, said machine-readable code configured tocause said processor to receive medical-event related information fromsaid one or more input devices, such medical-event related informationcomprising notification of a medical code event, information relating tothe medical code event, said information comprising one or more of:patient data or values, medical personnel present, prescribedmedications and treatments, medical events relating to the measurementof patient data or values, measurement of patient responses, applicationof said medications and said treatments; said machine-readable codefurther configured to cause said processor to apply timestamps to saidmedical events; said machine-readable code further configured to causesaid processor to store said information in said memory; saidmachine-readable code further configured to cause said processor togenerate additional medical information comprising one or more of:recommended medication, recommended treatment, recommended values forsaid recommended medication and said recommended treatment, recommendedtiming for application of said recommended medication and saidrecommended treatment, and information identifying any error or conflictin received medical information; and said machine-readable code furtherconfigured to cause said processor to generate one or more outputsrelated to said information regarding said medical code event and/orsaid generated additional information regarding said medical code eventfor output by said output devices.
 7. The device for processing medicalevent related information of claim 6, wherein said one or morecommunication links comprising one or more high-level securitycommunication links and one or more low-level security communicationlinks, said one or more high-level security communication linkscomprising one or more levels of security protocols and/or features tocontrol the ability to read, add, modify, or delete informationtransmitted via said one or more high-level security communicationlinks, and said one or more low-level security communication linkscomprising one or more levels of security protocols and/or features tocontrol the ability to read, add, modify, or delete informationtransmitted via said one or more low-level security communication links,such said one or more levels of security protocols and/or features ofsaid one or more high-level security communication links is higher thansaid one or more levels of security protocols and/or features of saidone or more low-level security communication links.
 8. The device forprocessing medical event related information of claim 6, wherein thememory comprising a secure memory and a non-secure memory, said securememory comprising one or more levels of security protocols and/orfeatures to control the ability to read, add, modify, or delete saidconfidential information stored in said secure memory, and saidnon-secure memory comprising one or more levels of security protocolsand/or features to control the ability to read, add, modify, or deletesaid confidential information stored in said non-secure memory, suchthat said one or more levels of security protocols and/or features ofsaid secure memory is higher than said one or more levels of securityprotocols and/or features of said non-secure memory.
 9. The device forprocessing medical-event related information of claim 6, wherein sendingsaid medical events and said additional medical information to said oneor more output devices causes display of some or all of said receivedmedical events and some or all of said additional medical information onsaid one or more output devices.
 10. The device for processingmedical-event related information of claim 6 further comprising: ananalog clock comprising time indicators; one or more media outputdevices comprising: patient value indicators to display said measuredpatient data or values and said measured patient responses; medicationindicators to indicate at least one of: (a) one or more administeredmedications and/or medical treatments and (b) generated medicationsand/or medical treatments; timing indicators to indicate a timing of oneor more of said medication indicators; and audio output devices toindicate one or more alerts relating to said medication indicators. 11.A system and processes to process medical-event related informationcomprising: a user device comprising: one or more input devicescomprising at least one of: one or more recording devices, one or morereading devices, one or more input/output devices, one or more userdevices, one or more medical devices, and/or one or more externalservers; one or more one output devices comprising at least one of: oneor more media output devices, one or more visual indicators, one or moredocument output devices, said one or more user devices, said one or moremedical devices, and/or said one or more external devices; one or moreoutput device; a memory; at least one controller; at least one servercomprising a processor; a communication link used for communicationbetween said one or more input devices, said one or more output device,said memory, said controller, and said server; machine-readable codestored in said memory and executed by said processor, saidmachine-readable code configured to cause said processor to receivemedical events relating to the measurement of patient data or values,measurement of patient responses, and application of medications andtreatments; said machine-readable code is further configured to causesaid processor to apply timestamps to said medical events; saidmachine-readable code further configured to cause said processor tostore said medical events in said memory; said machine-readable code isfurther configured to cause said processor to generate additionalmedical information comprising recommended medication, recommendedtreatment, recommended values for said recommended medication and saidrecommended treatment, and recommended timing for application of saidrecommended medication and said recommended treatment; saidmachine-readable code further configured to cause said processor to sendsaid medical events, said timestamps, and said additional medicalinformation to said one or more output devices.
 12. The system andprocesses to process medical-event related information of claim 11,wherein machine-readable code is further configured to send said medicalevents, timestamps, and said additional medical information to said oneor more output devices to cause the display of some or all of saidmedical events and some or all of said additional medical information tobe displayed on said one or more output devices.
 13. The system andprocesses to process medical-event related information of claim 11,wherein said machine-readable code is further configured to sort saidmedical events and said additional medical information into confidentialmedical information and non-confidential medical information, and tosend non-confidential medical information to said one or more outputdevices.
 14. The system and processes to process medical-event relatedinformation of claim 13, wherein machine-readable code is furtherconfigured to receive user credentials via said one or more inputdevices, to sort said user credentials into one or more clearancelevels, and to send to all confidential medical information to said oneor more output devices associated with high clearance level, to sendsome confidential medical information to said one or more output devicesassociated with a medium clearance level, and to send no confidentialmedical information to said one or more output devices associated with alow clearance level.